Skip to content

feat(ops): first-class key rotation (make rotate-key + runbook) - #18

Open
JosephOIbrahim wants to merge 1 commit into
masterfrom
feat/key-rotation-tooling
Open

feat(ops): first-class key rotation (make rotate-key + runbook)#18
JosephOIbrahim wants to merge 1 commit into
masterfrom
feat/key-rotation-tooling

Conversation

@JosephOIbrahim

Copy link
Copy Markdown
Owner

What

Makes API-key rotation a first-class, discoverable command.

The script itself — scripts/rotate_anthropic_key.sh — already shipped on master (bundled into #16's 3e0343e). This focused follow-up adds the tooling + docs around it:

  • make rotate-key — one command; runs the script (paste the new key, input hidden).
  • docs/key-rotation.md — a short runbook: rotate locally, then delete the old key in the console.

Why

The bare script landed bundled with a README change, so it wasn't discoverable on its own. This elevates it to a documented, one-command procedure.

The script validates the new key against the Anthropic API before changing anything, persists it (launchctl + a chmod 600 login agent), bounces the daemon, and never prints the key. The MCP coaching surface uses no Claude credential, so rotation never disrupts it.

🤖 Generated with Claude Code

scripts/rotate_anthropic_key.sh shipped on master bundled in #16 (3e0343e).
This focused PR makes it discoverable + documented:
- make rotate-key  — one command (paste new key, hidden, validate + persist)
- docs/key-rotation.md — runbook: rotate locally, then delete the old key in
  the Anthropic console.

The MCP coaching path uses no Claude credential, so rotation never disrupts it.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JosephOIbrahim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 minutes and 28 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4f18ca1a-c072-4aad-9c7c-9cd67c3b5f93

📥 Commits

Reviewing files that changed from the base of the PR and between be08561 and 17835c0.

📒 Files selected for processing (2)
  • Makefile
  • docs/key-rotation.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/key-rotation-tooling

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant